-
-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workaround botocore
bug in S3 URL Handler backend
#19056
Conversation
It would be good to avoid pushing branches to |
I don't disagree but thats more of an infrastructural issue with our stuff IMO. I make these branches in the GitHub UI which doesn't offer an option for committing to a fork if you can commit to origin. |
I can try and tackle the infra issues as well very soon. As the cherry picker will be pushing to |
See boto/botocore#2948 for the upstream bug fix. This only occurs for toekn-based auth, and therefore wasn't caught in tests or in local testing.
See boto/botocore#2948 for the upstream bug fix. This only occurs for toekn-based auth, and therefore wasn't caught in tests or in local testing.
…19056) (#19111) See boto/botocore#2948 for the upstream bug fix. This only occurs for toekn-based auth, and therefore wasn't caught in tests or in local testing. Co-authored-by: Joshua Cannon <joshdcannon@gmail.com>
…19056) (#19110) See boto/botocore#2948 for the upstream bug fix. This only occurs for toekn-based auth, and therefore wasn't caught in tests or in local testing. Co-authored-by: Joshua Cannon <joshdcannon@gmail.com>
UGH! Apparently this is the only place where they use lowercase |
See boto/botocore#2948 for the upstream bug fix.
This only occurs for toekn-based auth, and therefore wasn't caught in tests or in local testing.